Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1159

reference
366-tree-1
name
1159
tree-preservation-order

undefined

366-tpo-1
uprn
address-text
point
POINT (-1.018077 50.894345)
geometry
MULTIPOLYGON (((-1.018021 50.894339,-1.018023 50.894350,-1.018031 50.894360,-1.018043 50.894368,-1.018059 50.894373,-1.018077 50.894375,-1.018094 50.894374,-1.018110 50.894369,-1.018123 50.894361,-1.018131 50.894351,-1.018134 50.894340,-1.018132 50.894329,-1.018124 50.894319,-1.018111 50.894311,-1.018096 50.894305,-1.018078 50.894303,-1.018061 50.894305,-1.018045 50.894310,-1.018032 50.894318,-1.018024 50.894328,-1.018021 50.894339)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL